Clarify TTL document restore behavior in backup documentation #343
Conversation
- Updated periodic backup documentation to clarify that TTL-expired documents are not restored by default but behavior can be enforced explicitly - Updated continuous backup documentation with consistent language for restore behavior - Ensures both backup modes have aligned documentation about restoration options
|
@microsoft-github-policy-service agree company="Microsoft" |
|
@HansWieser-MS : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
prmerger-automator
bot
added
azure-cosmos-db/svc
Change sent to author
nosql/subsvc
labels
|
Learn Build status updates of commit 95d2047: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
prmerger-automator
bot
added
the
aq-pr-triaged
There was a problem hiding this comment.
Pull request overview
This PR clarifies the documentation about TTL-expired document restoration behavior in both periodic and continuous backup modes for Azure Cosmos DB.
Changes:
- Updated periodic backup documentation to clarify that TTL-expired documents are not restored by default, but the behavior can be enforced explicitly
- Updated continuous backup documentation with consistent TTL restore behavior language and reformatted the "What isn't restored?" list
- Ensured both backup modes have aligned documentation about TTL restoration options
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| articles/cosmos-db/periodic-backup-restore-introduction.md | Updated TTL restoration behavior statement to clarify default behavior and explicit enforcement option |
| articles/cosmos-db/continuous-backup-restore-introduction.md | Added TTL restoration statement and reformatted list items with proper markdown syntax |
Comments suppressed due to low confidence (1)
articles/cosmos-db/continuous-backup-restore-introduction.md:65
- The statement claims 'the behavior can be enforced explicitly' but there is no documentation in the codebase explaining how to explicitly enforce TTL-expired document restoration. This could confuse users who want to restore TTL-expired documents. Either add documentation explaining how to enforce this behavior, link to relevant documentation, or remove the claim if this feature doesn't exist or isn't documented.
- Documents that were deleted because of expired TTL are not restored by default, however the behavior can be enforced explicitly.
| - Stored procedures, triggers, user-defined functions (UDF). | ||
| - Role-based access control assignments. These need to be reassigned. | ||
| - Documents that were deleted because of expired TTL. | ||
| - Documents that were deleted because of expired TTL are not restored by default, however the behavior can be enforced explicitly. |
There was a problem hiding this comment.
The statement claims 'the behavior can be enforced explicitly' but there is no documentation in the codebase explaining how to explicitly enforce TTL-expired document restoration. This could confuse users who want to restore TTL-expired documents. Either add documentation explaining how to enforce this behavior, link to relevant documentation, or remove the claim if this feature doesn't exist or isn't documented.
|
@kanshiG, this is a pull request from a customer to update TTL details for backup/restore. |
4 participants
This PR clarifies the documentation about TTL-expired document restoration behavior in both periodic and continuous backup modes.
Changes Made:
This provides clearer guidance to users about TTL restoration behavior and helps users understand they can explicitly request TTL-expired document restoration when needed.